Detecting and processing sections spanning processed document partitions

ABSTRACT

Aspects of the invention include detecting and processing sections spanning processed document partitions by caching a document partition. The document partition includes metadata indicating that the document partition is a portion of a whole document. Aspects also include pairing a candidate paragraph from the document partition with a cached paragraph segment and determining, using a coherence model, a probability that the candidate paragraph and the cached paragraph segment constitute a semantically coherent paragraph. Aspects further include discarding the cached paragraph segment and processing the candidate paragraph and the cached paragraph segment separately based on a determination that the probability is less than a threshold level and processing the candidate paragraph and the cached paragraph segment together as a cross-partition paragraph based on a determination that the probability is greater than the threshold level.

BACKGROUND

The present invention generally relates to programmable computing systems, and more specifically, to detecting and processing sections spanning processed document partitions.

Information retrieval computing systems can receive search queries from a user and provide answers back to the user. In information retrieval, a question answering (QA) system is tasked with automatically answering a question posed in natural language to the system. A QA system can retrieve an answer by searching a data corpus for documents matching the search query. To assist the QA system, the documents are annotated to describe relationships between co-existing entities. The process of annotating documents is performed by subject matter experts who review the documents and determine whether any entities in the documents can be annotated. The annotations assist the QA system to retrieve the best documents to answer the search query.

SUMMARY

Embodiments of the present invention are directed to detecting and processing sections spanning processed document partitions. A non-limiting example computer-implemented method includes caching a document partition, the document partition including metadata indicating that the document partition is a portion of a whole document. The method also includes pairing a candidate paragraph from the document partition with a cached paragraph segment and determining, using a coherence model, a probability that the candidate paragraph and the cached paragraph segment constitute a semantically coherent paragraph. The method further includes discarding the cached paragraph segment and processing the candidate paragraph and the cached paragraph segment separately based on a determination that the probability is less than a threshold level and processing the candidate paragraph and the cached paragraph segment together as a cross-partition paragraph based on a determination that the probability is greater than the threshold level.

Other embodiments of the present invention implement features of the above-described method in computer systems and computer program products.

Additional technical features and benefits are realized through the techniques of the present invention. Embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed subject matter. For a better understanding, refer to the detailed description and to the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The specifics of the exclusive rights described herein are particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features and advantages of the embodiments of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:

FIG. 1 illustrates a block diagram of a system for detecting and processing sections spanning processed document partitions in accordance with one or more embodiments of the present invention;

FIG. 2 illustrates a whole document in accordance with one or more embodiments of the present invention;

FIG. 3 illustrates processed document partitions and associated metadata in accordance with one or more embodiments of the present invention;

FIG. 4 illustrates a flow diagram of a process for detecting and processing sections spanning processed document partitions in accordance with one or more embodiments of the present invention;

FIG. 5 illustrates a cloud computing environment according to one or more embodiments of the present invention;

FIG. 6 illustrates abstraction model layers according to one or more embodiments of the present invention; and

FIG. 7 illustrates a block diagram of a computer system for use in implementing one or more embodiments of the present invention.

The diagrams depicted herein are illustrative. There can be many variations to the diagrams or the operations described therein without departing from the spirit of the invention. For instance, the actions can be performed in a differing order or actions can be added, deleted or modified. Also, the term “coupled” and variations thereof describes having a communications path between two elements and does not imply a direct connection between the elements with no intervening elements/connections between them. All of these variations are considered a part of the specification.

DETAILED DESCRIPTION

One or more embodiments of the present invention provide computer-implemented methods and computing systems that receive a scanned image of an original text document and convert the image into machine-encodable text that has a same layout as the original text document. Information retrieval systems are operable to receive a search query and, in response, analyze structured data to retrieve an answer to the query. The structured data can be in the form of annotated electronic documents organized in a corpus. The annotations are extra information that describes various tokens and relationships between tokens found in the electronic documents. In many instances, the annotations are in the form of metadata and not visible to an end-user. In response to a search query, the information retrieval can retrieve an electronic document that potentially answers the query. The information retrieval system can retrieve the electronic documents based on keywords found in the text of the documents. The information retrieval system can further analyze the information contained in the documents by analyzing the annotations embedded in the documents.

In exemplary embodiments, the electronic documents are annotated using natural language processing techniques that identify the different sections in the text and insert annotations to describe the respective text of the sections. Many of the documents are originally paper documents that are scanned and digitized into electronic format. The electronic documents can be processed using optical character recognition (OCR) to convert the scanned text image into plain text or rich text. A plain text document only includes text without any special formatting. Rich-text document includes text with formatting, such as bold, text-size underlining, and the like. The electronic documents can further be processed to recreate electronic documents that resemble the original paper documents. For example, natural language processing techniques apply text analysis methods and rules to detect section headers and predict the beginning and sending of document sections.

Conventional document processing techniques have well-known shortcomings. For example, sections can be occluded due to graphics and colors used in an original document. In other instances, sections are not identified due to the lack of a section header or unknown header. These instances can result in multiple sections from the original paper document being converted into a single section in the electronic document. In one example, a single section can be improperly converted into multiple sections in instances when a section or paragraph spans a page break. As a result, the subject matter expert has an electronic document that is not properly divided into segments. This results in a more laborious annotation process.

One or more embodiments of the present invention address one or more of the above-described shortcomings by providing computer-implemented methods and computing systems to detect and process sections spanning processed document partitions. In exemplary embodiments, the document image is processed to identify different sections in the document image.

Turning now to FIG. 1, a system 100 for detecting and processing sections spanning processed document partitions is generally shown in accordance with one or more embodiments of the present invention. The system 100 includes a conversion unit 102 for receiving a document image and converting any text found in the image into a machine-encodable text, for example, plain text. The system 100 further includes a machine learning unit 104 that is trained to detect objects in the image. The objects include sections (e.g. blocks of text, paragraphs, bullet points) found in the document image. The system 100 further includes a formatting unit 106 for embedding the machine-encodable text file with metadata that describes the layout of the detected objects.

The conversion unit 102 is operable to receive an electronic document image 108 and convert the text found in the document image 108 to machine-encodable text. In some embodiments of the present invention, the conversion unit 102 can use optical character recognition (OCR) to perform the conversion. In general, the conversion unit 102 can receive the document image 108 or a bitmap describing the image and identify dark and light areas. The conversion unit 102 can further analyze the dark areas for the presence of alphanumeric characters (text). The conversion unit 102 can apply various methods to determine if the dark area contains any text. For example, the conversion unit 102 can use pattern recognition, in which the conversion unit 102 can compare and recognize the shapes formed by the dark areas with example alphanumeric characters in different fonts and font sizes. The conversion unit 102 can also apply feature detection, in which the conversion unit 102 can be trained to recognize different features such as a number of curves or arrangement or curved and straight lines. For example, the letter “P” can be a combination of a straight line and an arc at one end of the straight line. Once an alphanumeric character is recognized, it can be converted to an encoding standard such as the American Standard Code for Information (ASCII) or other appropriate encoding standard based upon language and geographic location. A computing system can read the ASCII code for the alphanumeric character and generate the corresponding letter or number. Once the conversion unit 102 has identified each alphanumeric character in the image, it can convert the text from the image into machine-encodable text, such as a plain text or a rich text format.

The machine learning unit 104 can further extract features and analyze the features to determine the boundaries of different sections in the document image 108. In some embodiments of the present invention, the machine learning unit can include a convolutional neural network-based classifier. For example, the machine learning unit 104 can use a Regional Convolutional Neural Network (R-CNN). The R-CNN can receive document image 108 and detect objects contained therein. The objects include different sections of the document, including but not limited to paragraphs of text, figures, bullet points, titles, conclusions, and other natural sections of a document. In some embodiments of the present invention, the R-CNN first generates bounding boxes in document image 108 to find candidate sections and runs a classifier on each bounding box. The R-CNN further determines a location and dimension of each bounding box. The R-CNN analyzes the extracted features to determine whether a bounding box encapsulates one or more sections. The R-CNN can be trained to detect features that suggest distinct text blocks. The features can include offsets between text blocks, underlined or bolded words at the beginning of a text block, spacing, punctuation, capitalized strings of text, graphical indicator (e.g., box surrounding text), formatting (e.g., bolding, underlining), or other appropriate features. Upon classification of different objects, the R-CNN removes duplicate classifications and scores the boxes based on the other detected objects in the image. The highest scoring bounding boxes are classified as sections. The objects can take the form of geometric shapes that distinguish the different sections of the original document.

It should be appreciated that a classification type of object is not necessary for object detection. In some embodiments of the present invention, the machine learning unit 104 does recognize the alphanumeric characters at the beginning and end of the section encapsulated by a box. In other embodiments, each alphanumeric character in an image can be indexed, and the machine learning unit 104 recognizes and index number of the beginning and ending character of each text block. However, the machine learning unit 104 does not need to recognize the substance of each text block. In other words, the machine learning unit 104 does not need to describe the purpose or subject matter of an object. The purpose of subject matter can include but not be limited to a title block, patient medical history, diagnosis, or conclusion. Rather, the machine learning unit 104 detects the beginning and ending of distinct sections without deriving meaning from the sections.

The phrases “neural network” and “machine learning” broadly describes a function of electronic systems that learn from data. A machine learning system, engine, or module can include a machine learning algorithm that can be trained, such as in an external cloud environment (e.g., the cloud computing environment 50), to learn functional relationships between inputs and outputs that are currently unknown. In one or more embodiments, machine learning functionality can be implemented using a machine learning unit 106 having the capability to be trained to perform a currently unknown function. In machine learning and cognitive science, neural networks are a family of statistical learning models inspired by the biological neural networks of animals, and in particular, the brain. Neural networks can be used to estimate or approximate systems and functions that depend on a large number of inputs.

The machine learning unit 104 can be embodied as so-called “neuromorphic” systems of interconnected processor elements that act as simulated “neurons” and exchange “messages” between each other in the form of electronic signals. Similar to the so-called “plasticity” of synaptic neurotransmitter connections that carry messages between biological neurons, the connections in the machine learning unit 104 that carry electronic messages between simulated neurons are provided with numeric weights that correspond to the strength or weakness of a given connection. During training, the weights can be adjusted and tuned based on experience, making the machine learning unit 104 adaptive to inputs and capable of learning. After being weighted and transformed by a function determined by the network's designer, the activation of these input neurons are then passed to other downstream neurons, which are often referred to as “hidden” neurons. This process is repeated until an output neuron is activated. The activated output neuron determines which character was read.

The formatting unit 106 is operable to map the objects detected by the machine learning unit 104 back on to the machine-encodable text generated by the conversion unit 102. The formatting unit 106 receives data describing each object from the machine learning unit 104 and encodes the machine-encodable text with metadata describing each object. The metadata respectively describes the boundaries and location of each section. The boundaries and location can be in relation to each other sections, a perimeter of the original document, or both. The formatting unit 106 reformats the machine-encodable text such that layout of the sections conform to the layout of the sections in the document image 108. The formatting unit 106 detects the beginning alphanumeric character and the ending alphanumeric character of a text block in a section. The formatting unit 106 arranges the location of the sections. This results in the machine-encodable text having the same layout as arranged in the document image 108.

The system is further operable to transmit the reformatted machine-encodable text to a natural language processing (NLP) unit 110. The NLP unit 110 can apply natural language processing techniques to semantically analyze the text, including determining entities to describe the text, and relationships between textual phrases. Based on the textual analysis and the identified segments, the NLP unit 110 can annotate the reformatted machine-encodable text with metadata.

The document image 108 can be a scanned image of a paper document, a portable document format (PDF) file, an image captured by an image capturing device, or other form of document image. The document image 108 can be an image of an original paper document, for example, a health care patient's medical records.

In exemplary embodiments, the document image is saved as multiple document partitions that each include a part of a whole document. Each document partition includes metadata that includes a identification of the whole document, such as a unique document ID, an indication of a number of total partitions in the whole document, and a partition identification number that identifies the partition. In one example, the metadata includes document ID (1234), partition number (1), and the number of partitions (3), which indicates that the current document partition is the first of three document partitions that make up document 1234.

Referring to FIG. 2, a whole document 200 in accordance with one or more embodiments of the present invention is shown. In exemplary embodiments, prior to processing of the document 200, by for example system 100, the document 200 is divided into multiple partitions 206, along line 205. In one embodiment, the size of the partitions 206 is determined based on a size of a cache used for processing the document partitions. As illustrated, in some cases, a paragraph 208 is be split across two partitions 206. In addition, the document 200 includes a plurality of sections 202. In some cases, a section 202, although not in the middle of a paragraph 208, is split across two partitions 206. When sections and/or paragraphs are split across partitions 206, portions of the sections and/or paragraphs are separated from their corresponding header 204. As a result, these portions of sections and/or paragraphs are not properly annotated with the data from their corresponding header 204.

FIG. 3 illustrates processed document partitions 310 and associated metadata 316 in accordance with one or more embodiments of the present invention. In exemplary embodiments, the metadata 316 includes an identification of the whole document, such as a document identification (DID), an indication of a number of total partitions in the whole document, and a partition identification number that identifies the partition. The document partitions 310 include sections 302 that have associated headers 304. In addition, the document partitions 310 include paragraphs 312, 314 that have been split across multiple partitions 310.

Referring to FIG. 4, a flow diagram of a method 400 for detecting and processing sections spanning processed document partitions is shown. As shown at block 402, the method 400 includes caching a document partition, the document partition including metadata indicating that the document partition is a portion of a whole document. In exemplary embodiments, the metadata includes an indication of a total number of partitions in the whole document and an indication of a partition number of the document partition. Next, as shown at block 404, the method 400 includes pairing a candidate paragraph from the document partition with a cached paragraph segment.

In exemplary embodiments, the candidate paragraph is one of a first and a last paragraph of the document partition and the candidate paragraph is determined based at least in part upon the metadata. In one embodiment, the candidate paragraph is identified as the last paragraph of the document partition based on the metadata indicating that the document partition is a first partition of the whole document. In exemplary embodiments, the cached paragraph segment is one of a first and a last paragraph of another document partition of the whole document.

Next, as shown at block 406, the method 400 includes determining, using a coherence model, a probability that the candidate paragraph and the cached paragraph segment constitute a semantically coherent paragraph. In exemplary embodiments, the coherence model includes one or more known coherence models such as a topic model, a semantic model, and an entity model that are leveraged to determine the probability of the two-paragraph segments constitute a whole, semantically coherent paragraph. Based on a determination that the probability is less than a threshold level, the method 400 proceeds to block 412 and discards the cached paragraph segment and processes the candidate paragraph and the cached paragraph segment separately. Otherwise, the method 400 proceeds to block 410 and processes the candidate paragraph and the cached paragraph segment together as a cross-partition paragraph.

In one embodiment, processing the candidate paragraph and the cached paragraph segment together as the cross-partition paragraph includes injecting the cached paragraph segment into the document partition and adjusting annotation offsets in a natural language process output to reflect character offsets as they pertain to the document partition. The annotation offsets over the cached paragraph injected from the cache contain pointers to a document partition from which the cached paragraph originated and the character offsets correspond to the text in the document in which they originate.

In another embodiment, processing the candidate paragraph and the cached paragraph segment together as the cross-partition paragraph includes extracting the candidate paragraph from the document partition, combining the candidate paragraph with the cached paragraph segment, and processing results of the combining as an interim document. The annotations within the interim document are returned alongside annotations from the whole document with pointers to the document partitions in which they originate including character offsets corresponding to where the text occurs in the partition that was processed.

In one embodiment, a request to process a document partition is received. The document partition includes metadata that indicates that the document partition is y of x partitions of a whole document. Based on the metadata, one or more of one or more portions of the document partition are transiently cached. The cached portion can include the last paragraph of the first document partition, the first paragraph of the last document partition, and the first and last paragraphs of intervening document partitions.

When a document partition is received and a candidate paragraph prefix/suffix has previously been processed and transiently cached, the candidate prefix/suffix from the input document is paired with its cached counterpart and coherence models (topic, semantic, entity, etc.) are leveraged to determine the probability of the two paragraph segments constituting a whole, semantically coherent paragraph. Based on a determination that the two paragraph segments are deemed to be topically/semantically disjointed, the cached segment is discarded and the document is processed in a typical fashion. However, based on a determination that the two paragraph segments are deemed topically/semantically coherent, this detected cross-request paragraph may be processed in a couple different ways, depending on the embodiment.

In one embodiment, the cached paragraph prefix/suffix is injected into the input document, and the document is processed in a typical fashion. Annotation offsets are adjusted in the NLP process output to reflect the character offsets as they pertain to the canonical input document. Annotations over the paragraph segment injected from the cache, contain pointers to the document partition from which they originate. The character offsets correspond to the text in the canonical document in which they originate.

In another embodiment, the paragraph prefix/suffix from the input document is extracted and combined with the cached paragraph prefix/suffix, and this whole paragraph is processed as a separate interim document. Annotations within the interim document are returned alongside annotations from the canonical document with pointers to the document partitions in which they originate, including character offsets corresponding to where the text occurs in the canonical partition that was processed.

In exemplary embodiments, the document partitions can be processed in the order that they appear in the whole document or reverse order. For example, when processing document partitions in the order the partitions appear in the document, when processing the first document, only the last paragraph of the document partition is cached. Likewise, when processing the last document partition only the first paragraph of the document partition is cached. However, when processing intervening document partitions, both the first and last paragraphs are cached. When processing a document partition, a determination is made as to whether the proceeding document partition has been processed and, if so, the last paragraph of a previously processed document is obtained from the cache. That paragraph is evaluated for semantic coherence with the first paragraph of the input document to determine how likely is it that these two paragraphs were one paragraph in the canonical document.

It is to be understood that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.

Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.

Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure that includes a network of interconnected nodes.

Referring now to FIG. 5, illustrative cloud computing environment 50 is depicted. As shown, cloud computing environment 50 includes one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54A, desktop computer 54B, laptop computer 54C, and/or automobile computer system 54N may communicate. Nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 50 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 54A-N shown in FIG. 5 are intended to be illustrative only and that computing nodes 10 and cloud computing environment 50 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring now to FIG. 6, a set of functional abstraction layers provided by cloud computing environment 50 (FIG. 5) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 6 are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and software components. Examples of hardware components include: mainframes 61; RISC (Reduced Instruction Set Computer) architecture based servers 62; servers 63; blade servers 64; storage devices 65; and networks and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71; virtual storage 72; virtual networks 73, including virtual private networks; virtual applications and operating systems 74; and virtual clients 75.

In one example, management layer 80 may provide the functions described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may include application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.

Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analytics processing 94; transaction processing 95; and section detection 96.

It is understood that the present disclosure is capable of being implemented in conjunction with any other type of computing environment now known or later developed. For example, FIG. 7 depicts a block diagram of a processing system 700 for implementing the techniques described herein. In examples, the processing system 700 has one or more central processing units (processors) 721 a, 721 b, 721 c, etc. (collectively or generically referred to as processor(s) 721 and/or as processing device(s)). In aspects of the present disclosure, each processor 721 can include a reduced instruction set computer (RISC) microprocessor. Processors 721 are coupled to system memory (e.g., random access memory (RAM) 724) and various other components via a system bus 733. Read only memory (ROM) 722 is coupled to system bus 733 and may include a basic input/output system (BIOS), which controls certain basic functions of the processing system 700.

Further depicted are an input/output (I/O) adapter 727 and a network adapter 726 coupled to the system bus 733. I/O adapter 727 may be a small computer system interface (SCSI) adapter that communicates with a hard disk 723 and/or a storage device 725 or any other similar component. I/O adapter 727, hard disk 723, and storage device 725 are collectively referred to herein as mass storage 734. Operating system 740 for execution on processing system 700 may be stored in mass storage 734. The network adapter 726 interconnects system bus 733 with an outside network 736 enabling processing system 700 to communicate with other such systems.

A display (e.g., a display monitor) 735 is connected to the system bus 733 by display adapter 732, which may include a graphics adapter to improve the performance of graphics intensive applications and a video controller. In one aspect of the present disclosure, adapters 726, 727, and/or 732 may be connected to one or more I/O busses that are connected to the system bus 733 via an intermediate bus bridge (not shown). Suitable I/O buses for connecting peripheral devices such as hard disk controllers, network adapters, and graphics adapters typically include common protocols, such as the Peripheral Component Interconnect (PCI). Additional input/output devices are shown as connected to system bus 733 via user interface adapter 728 and display adapter 732. An input device 729 (e.g., a keyboard, a microphone, a touchscreen, etc.), an input pointer 730 (e.g., a mouse, trackpad, touchscreen, etc.), and/or a speaker 731 may be interconnected to system bus 733 via user interface adapter 728, which may include, for example, a Super I/O chip integrating multiple device adapters into a single integrated circuit.

In some aspects of the present disclosure, the processing system 700 includes a graphics processing unit 737. Graphics processing unit 737 is a specialized electronic circuit designed to manipulate and alter memory to accelerate the creation of images in a frame buffer intended for output to a display. In general, graphics processing unit 737 is very efficient at manipulating computer graphics and image processing and has a highly parallel structure that makes it more effective than general-purpose CPUs for algorithms where processing of large blocks of data is done in parallel.

Thus, as configured herein, the processing system 700 includes processing capability in the form of processors 721, storage capability including system memory (e.g., RAM 724), and mass storage 734, input means such as keyboard 729 and mouse 730, and output capability including speaker 731 and display 735. In some aspects of the present disclosure, a portion of system memory (e.g., RAM 724) and mass storage 734 collectively store the operating system 740 to coordinate the functions of the various components shown in the processing system 700.

Various embodiments of the invention are described herein with reference to the related drawings. Alternative embodiments of the invention can be devised without departing from the scope of this invention. Various connections and positional relationships (e.g., over, below, adjacent, etc.) are set forth between elements in the following description and in the drawings. These connections and/or positional relationships, unless specified otherwise, can be direct or indirect, and the present invention is not intended to be limiting in this respect. Accordingly, a coupling of entities can refer to either a direct or an indirect coupling, and a positional relationship between entities can be a direct or indirect positional relationship. Moreover, the various tasks and process steps described herein can be incorporated into a more comprehensive procedure or process having additional steps or functionality not described in detail herein.

One or more of the methods described herein can be implemented with any or a combination of the following technologies, which are each well known in the art: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.

For the sake of brevity, conventional techniques related to making and using aspects of the invention may or may not be described in detail herein. In particular, various aspects of computing systems and specific computer programs to implement the various technical features described herein are well known. Accordingly, in the interest of brevity, many conventional implementation details are only mentioned briefly herein or are omitted entirely without providing the well-known system and/or process details.

In some embodiments, various functions or acts can take place at a given location and/or in connection with the operation of one or more apparatuses or systems. In some embodiments, a portion of a given function or act can be performed at a first device or location, and the remainder of the function or act can be performed at one or more additional devices or locations.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, element components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The embodiments were chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.

The diagrams depicted herein are illustrative. There can be many variations to the diagram or the steps (or operations) described therein without departing from the spirit of the disclosure. For instance, the actions can be performed in a differing order or actions can be added, deleted or modified. Also, the term “coupled” describes having a signal path between two elements and does not imply a direct connection between the elements with no intervening elements/connections therebetween. All of these variations are considered a part of the present disclosure.

The following definitions and abbreviations are to be used for the interpretation of the claims and the specification. As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having,” “contains” or “containing,” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a composition, a mixture, process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but can include other elements not expressly listed or inherent to such composition, mixture, process, method, article, or apparatus.

Additionally, the term “exemplary” is used herein to mean “serving as an example, instance or illustration.” Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. The terms “at least one” and “one or more” are understood to include any integer number greater than or equal to one, i.e. one, two, three, four, etc. The terms “a plurality” are understood to include any integer number greater than or equal to two, i.e. two, three, four, five, etc. The term “connection” can include both an indirect “connection” and a direct “connection.”

The terms “about,” “substantially,” “approximately,” and variations thereof, are intended to include the degree of error associated with measurement of the particular quantity based upon the equipment available at the time of filing the application. For example, “about” can include a range of ±8% or 5%, or 2% of a given value.

The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instruction by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments described herein. 

What is claimed is:
 1. A method for detecting and processing sections spanning processed document partitions, the method comprising: caching a document partition, the document partition including metadata indicating that the document partition is a portion of a whole document; pairing a candidate paragraph from the document partition with a cached paragraph segment; determining, using a coherence model, a probability that the candidate paragraph and the cached paragraph segment constitute a semantically coherent paragraph; discarding the cached paragraph segment and processing the candidate paragraph and the cached paragraph segment separately based on a determination that the probability is less than a threshold level; and processing the candidate paragraph and the cached paragraph segment together as a cross-partition paragraph based on a determination that the probability is greater than the threshold level.
 2. The method of claim 1, wherein the metadata includes an indication of a total number of partitions in the whole document and an indication of a partition number of the document partition.
 3. The method of claim 2, wherein the candidate paragraph is one of a first and a last paragraph of the document partition and wherein the candidate paragraph is determined based at least in part upon the metadata.
 4. The method of claim 2, wherein the candidate paragraph is identified as the last paragraph of the of the document partition based on the metadata indicating that the document partition is a first partition of the whole document.
 5. The method of claim 1, wherein the cached paragraph segment is one of a first and a last paragraph of another document partition of the whole document.
 6. The method of claim 1, wherein processing the candidate paragraph and the cached paragraph segment together as the cross-partition paragraph comprises: injecting the cached paragraph segment into the document partition; and adjusting annotation offsets in a natural language process output to reflect character offsets as they pertain to the document partition, wherein annotation offsets over the cached paragraph injected from the cache contain pointers to a document partition from which the cached paragraph originated, and wherein the character offsets correspond to the text in the document in which they originate.
 7. The method of claim 1, the candidate paragraph and the cached paragraph segment together as the cross-partition paragraph comprises: extracting the candidate paragraph from the document partition; combining the candidate paragraph with the cached paragraph segment, and processing results of the combining as an interim document, wherein annotations within the interim document are returned alongside annotations from the whole document with pointers to the document partitions in which they originate including character offsets corresponding to where the text occurs in the partition that was processed.
 8. A system comprising: a memory having computer readable instructions; and one or more processors for executing the computer readable instructions, the computer readable instructions controlling the one or more processors to perform operations comprising: caching a document partition, the document partition including metadata indicating that the document partition is a portion of a whole document; pairing a candidate paragraph from the document partition with a cached paragraph segment; determining, using a coherence model, a probability that the candidate paragraph and the cached paragraph segment constitute a semantically coherent paragraph; discarding the cached paragraph segment and processing the candidate paragraph and the cached paragraph segment separately based on a determination that the probability is less than a threshold level; and processing the candidate paragraph and the cached paragraph segment together as a cross-partition paragraph based on a determination that the probability is greater than the threshold level.
 9. The system of claim 8, wherein the metadata includes an indication of a total number of partitions in the whole document and an indication of a partition number of the document partition.
 10. The system of claim 9, wherein the candidate paragraph is one of a first and a last paragraph of the document partition and wherein the candidate paragraph is determined based at least in part upon the metadata.
 11. The system of claim 10, wherein the candidate paragraph is identified as the last paragraph of the of the document partition based on the metadata indicating that the document partition is a first partition of the whole document.
 12. The system of claim 8, wherein the cached paragraph segment is one of a first and a last paragraph of another document partition of the whole document.
 13. The system of claim 8, wherein processing the candidate paragraph and the cached paragraph segment together as the cross-partition paragraph comprises: injecting the cached paragraph segment into the document partition; and adjusting annotation offsets in a natural language process output to reflect character offsets as they pertain to the document partition, wherein annotation offsets over the cached paragraph injected from the cache contain pointers to a document partition from which the cached paragraph originated, and wherein the character offsets correspond to the text in the document in which they originate.
 14. The system of claim 8, the candidate paragraph and the cached paragraph segment together as the cross-partition paragraph comprises: extracting the candidate paragraph from the document partition; combining the candidate paragraph with the cached paragraph segment, and processing results of the combining as an interim document, wherein annotations within the interim document are returned alongside annotations from the whole document with pointers to the document partitions in which they originate including character offsets corresponding to where the text occurs in the partition that was processed.
 15. A computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to perform operations comprising: caching a document partition, the document partition including metadata indicating that the document partition is a portion of a whole document; pairing a candidate paragraph from the document partition with a cached paragraph segment; determining, using a coherence model, a probability that the candidate paragraph and the cached paragraph segment constitute a semantically coherent paragraph; discarding the cached paragraph segment and processing the candidate paragraph and the cached paragraph segment separately based on a determination that the probability is less than a threshold level; and processing the candidate paragraph and the cached paragraph segment together as a cross-partition paragraph based on a determination that the probability is greater than the threshold level.
 16. The computer program product of claim 15, wherein the metadata includes an indication of a total number of partitions in the whole document and an indication of a partition number of the document partition.
 17. The computer program product of claim 16, wherein the candidate paragraph is one of a first and a last paragraph of the document partition and wherein the candidate paragraph is determined based at least in part upon the metadata.
 18. The computer program product of claim 17, wherein the candidate paragraph is identified as the last paragraph of the of the document partition based on the metadata indicating that the document partition is a first partition of the whole document.
 19. The computer program product of claim 15, wherein the cached paragraph segment is one of a first and a last paragraph of another document partition of the whole document.
 20. The computer program product of claim 15, wherein processing the candidate paragraph and the cached paragraph segment together as the cross-partition paragraph comprises: injecting the cached paragraph segment into the document partition; and adjusting annotation offsets in a natural language process output to reflect character offsets as they pertain to the document partition, wherein annotation offsets over the cached paragraph injected from the cache contain pointers to a document partition from which the cached paragraph originated, and wherein the character offsets correspond to the text in the document in which they originate. 